% subsection of Project Overview Statement

\section{Assumptions}

This section is intended to provide the authors' assumptions regarding the
project performance influenced by risks and hindrances.

\subsection{Risks}

\risktable{Requirement Understanding}
{high}
{Requirements are only partly known at project start.}
{Fixate high level clients requirements at early stage. Meet regularly with
client and professionals to evaluate requirements understanding.}

\risktable{User impact understanding}
{high}
{Difficulties in understanding impact on users. Project team has no contact to
real end users.} 
{Frequent meetings with client to enable lifelike development cases.}

\risktable{Project Scope}
{medium}
{Size of project task exceeds timeframe.}
{Talking to the client and professionals in the field (Gilles, Nigel) to get
input and feedback about used technology and approaches. Splitting project into
several cycles to be able to deliver a working prototypical part if needed
\cite{wysocki}.}

\risktable{System familiarity}
{medium}
{Project members lack insight into field of profession and technologies.}
{Get in touch with professionals of the field (Nigel, Gilles). Get frequent
feedback from clients, supervisor and professionals.}

\risktable{Data Storage}
{medium}
{Loss of data due to hardware failures or hardware theft.}
{Storing all project related information on a network machine with daily backup
routines (see \autoref{sec:infrastructure}).}

\risktable{Testing difficulty}
{medium}
{Testing environment, guidelines and timeframe are unclear.}
{Test early and involve the client into the testing.}

\risktable{Commitment}
{low}
{Lack of client commitment.}
{Involve client in project work and frequently show results to highlight
project benefits.}

\risktable{Integration time}
{low}
{Estimated integration time is longer than expected.}
{Use of shared version control system for continuous integration of all
developers' work (see \autoref{sec:infrastructure}).}

\risktable{Communication}
{low}
{Communication problems in development team, which is dispersed among several
sites.} 
{Use of a source code version control system to enable continuous
collaboration. Make use of a dedicated project space to achive developer
collocation.}

\risktable{Requirements}
{low}
{Stated requirements might not match the customers' desires for the system.}
{Evaluating requirements with customer in consequent meetings. Ensure
understanding of requirements by prototypical implementations and customer feedback.}


\subsection{Feasibility}

%% SWOT MATRIX
\begin{center}%
\begin{table}[htb]

\begin{tabular}{| p{0.45\textwidth} || p{0.45\textwidth} |}%
\hline%
\sffamily\textbf{Strengths} & \sffamily\textbf{Weaknesses} \\
\hline%
\begin{description} %% here the strengths
  \item[Expertise] The project members are familiar with all needed aspects of
  the development environment. This includes Linux, Eclipse, Subversion and
  Java. Therefore no introductory training for these topics is needed at the
  start of the project.
  \item[Motivation] The project members are highly motivated.
\end{description} & \begin{description} %% here the weaks
  \item[Project insight] Project members had no prior contact with the
  project environment. This might cause problems in understanding the clients
  needs.
\end{description}
\\%
\hline%
\hline%
\sffamily\textbf{Opportunities} & \sffamily\textbf{Threats} \\
\hline%
\begin{description} %% here the opportunities
  \item[Deadline] The project is part of a bigger project that has a due date
  which corresponds with the deadline of the subproject. This might provide
  additional client commitment.
  \item[Client location] The clients are located on campus, which makes it easy
  to come along. 
  \end{description} & \begin{description} %% here the threats
  \item[Deadline] Since two deadlines fall together, the client might be too
  occupied to participate in testing and frequent meetings.
\end{description}
\\%
\hline%

\end{tabular}%
\caption{SWOT matrix}
\label{tab:swot}
\end{table}
\end{center}


\begin{description}
  \item[General View] Due to the high complexity of this project and the short
  timeframe, the project members hope to be able to keep the risks low and to
  overcome the possible hindrances. But since this
  is an intersting project and the project members have a high motivation, they are confident to achieve the
  stated goal.
  \item[Economical view] Project task is to solve a real world problem coming
  out of a development effort at the James Cook University in Townsville Australia.
  The client is the computer science branch at the JCU that is currently
  working on the senser network.(better name project description) Since the
  project is part of a student assignment inside a project class, high commitment of project particants can be assumed. Additionally the costs for this project do not involve any costs to pay the project members and are therefore limited to hardware costs of development equipment and costs of communication with the client. Therefore, the JCU will lessen the costs to develop the needed functionality by freeing internal ressources by outsourcing the described tasks of section 2 \& 3
of this document.
\end{description}


